<?xml version="1.0" encoding="utf-8"?>
<Content xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:blueonionsoftware-com:bloget:runtime:data">
  <text>from an MS blog...

So you're debugging your program, and all of a sudden you get this wierd error code - say error 0x00000011.  How do you know what that message means?

Well, one way is to memorize the entire Win32 error return code set, but that's got some issues.

Another way, if you have the right debugger extension is to use the !error extension - it will return the error text associated with the error.  There's a similar trick for dev studio (although I'm not sure what it is since I don't use the devstudio debugger)

But sometimes you're not running under windbg or devstudio and you've got a Win32 error code to look up.

And here's where the clever trick comes in.  You see, there's a complete list of error codes built into the system.  It's buried in the NET.EXE command that's used for network administration.

If you type "NET HELPMSG &lt;errorno&gt;" on the command line, you'll get a human readable version of the error code. 

So:

&lt;pre&gt;
C:\&gt;net helpmsg 17
&lt;/pre&gt;

The system cannot move the file to a different disk drive.

It's a silly little trick, but I've found it extraordinarily useful.&lt;/errorno&gt;</text>
  <last_update>2007-10-04T00:52:31.5990806Z</last_update>
  <source_title />
  <source_link />
  <comments />
  <references />
  <attachments />
</Content>